Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 17d1b53d904d457c2fee15409dc8db6bc9574d63643241fa1f8a7bacfa9ae2d9

Tx prefix hash: bba37de083c37dddb1e7e0a2ce4d5173714317bc9ce14c0ac0632937f1c5a4d9
Tx public key: 31927fbaf6f1ab79c525ddbb4051f5abe6fbf0d0b0c26c4e1e6d181a56ba5dda
Timestamp: 1710693872 Timestamp [UCT]: 2024-03-17 16:44:32 Age [y:d:h:m:s]: 00:314:15:06:48
Block: 980423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225154 RingCT/type: yes/0
Extra: 0131927fbaf6f1ab79c525ddbb4051f5abe6fbf0d0b0c26c4e1e6d181a56ba5dda02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08906d7742cc28ee0b696f45d1a263ede16c64b468169a93e1ac4a804950bd34 0.600000000000 1440488 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 980433, "vin": [ { "gen": { "height": 980423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08906d7742cc28ee0b696f45d1a263ede16c64b468169a93e1ac4a804950bd34" } } ], "extra": [ 1, 49, 146, 127, 186, 246, 241, 171, 121, 197, 37, 221, 187, 64, 81, 245, 171, 230, 251, 240, 208, 176, 194, 108, 78, 30, 109, 24, 26, 86, 186, 93, 218, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8