Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1810a6aa976e1fd4d10e0dc44cb020276ec070673c79c247915bed737eed2838

Tx prefix hash: 24c9a5fd4a406d5908969568e284c7851acae4977e1dc965c1ce8aa1e31bdfd2
Tx public key: 71c3a00f7120fde78791fbd2fb3fc2e8f6e7199b15e83d53455a800cd6997fc1
Timestamp: 1745609126 Timestamp [UCT]: 2025-04-25 19:25:26 Age [y:d:h:m:s]: 00:207:05:32:11
Block: 1269358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145827 RingCT/type: yes/0
Extra: 0171c3a00f7120fde78791fbd2fb3fc2e8f6e7199b15e83d53455a800cd6997fc1021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6da396ff7e8daab7cba31d950ff19cd5b5e7a90e997afa5744cd6458919bf70 0.600000000000 1756593 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": 1269368, "vin": [ { "gen": { "height": 1269358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6da396ff7e8daab7cba31d950ff19cd5b5e7a90e997afa5744cd6458919bf70" } } ], "extra": [ 1, 113, 195, 160, 15, 113, 32, 253, 231, 135, 145, 251, 210, 251, 63, 194, 232, 246, 231, 25, 155, 21, 232, 61, 83, 69, 90, 128, 12, 214, 153, 127, 193, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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