Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ab9f6d34d6bceb4e2a41da3fde424b1e7c3c0b1a6a2e359c2e2261f304c0bce

Tx prefix hash: a8feea62e209c731ab3cfa71f33d228e79aedd63accc7737b9d71a964fc0bdab
Tx public key: 6fb6c6d2990283d3e97b1f9690a8025f395d5112f9a4679d324c290bb5b93d0a
Timestamp: 1735580815 Timestamp [UCT]: 2024-12-30 17:46:55 Age [y:d:h:m:s]: 00:111:10:00:47
Block: 1186587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79426 RingCT/type: yes/0
Extra: 016fb6c6d2990283d3e97b1f9690a8025f395d5112f9a4679d324c290bb5b93d0a021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 456dddd416adb4349a6ca67d83c012d060736fbc7a53c9355b8e756c44eba1b6 0.600000000000 1673070 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": 1186597, "vin": [ { "gen": { "height": 1186587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "456dddd416adb4349a6ca67d83c012d060736fbc7a53c9355b8e756c44eba1b6" } } ], "extra": [ 1, 111, 182, 198, 210, 153, 2, 131, 211, 233, 123, 31, 150, 144, 168, 2, 95, 57, 93, 81, 18, 249, 164, 103, 157, 50, 76, 41, 11, 181, 185, 61, 10, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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