Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 484ddc1267026cede30c259f6f54dd4c4108c16b719d542ef3230323d771dfd4

Tx prefix hash: 11909fe2e9e7e41e3fbe2b9f79f39341ea237e627c49a06581a42bb7298f286f
Tx public key: dc04ba718ea5ffbe2a83f3a4709ddc62edf6caf0952c4a7e87d71d51aead6084
Timestamp: 1699055465 Timestamp [UCT]: 2023-11-03 23:51:05 Age [y:d:h:m:s]: 01:146:20:09:03
Block: 884117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365944 RingCT/type: yes/0
Extra: 01dc04ba718ea5ffbe2a83f3a4709ddc62edf6caf0952c4a7e87d71d51aead6084021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.722026889000 dcy

stealth address amount amount idx
00: 3e17ba8f12f5dadd7d8a2965ad2c75feab5cbaca134c243bca85dab9af7ab0a6 0.722026889000 1339850 of 0

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": 884127, "vin": [ { "gen": { "height": 884117 } } ], "vout": [ { "amount": 722026889, "target": { "key": "3e17ba8f12f5dadd7d8a2965ad2c75feab5cbaca134c243bca85dab9af7ab0a6" } } ], "extra": [ 1, 220, 4, 186, 113, 142, 165, 255, 190, 42, 131, 243, 164, 112, 157, 220, 98, 237, 246, 202, 240, 149, 44, 74, 126, 135, 215, 29, 81, 174, 173, 96, 132, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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