Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f42f14de2d066be7e179a7fe0d5f9f00045c5ff7515bf1df71612eb8cdeafd1

Tx prefix hash: f1cfac92e83043a1c0d2d9aa837b68bb7d1bf16b805f3eaab5d7105af05e027c
Tx public key: f84aa7ea765aa537b600019709f5b12dfea501f8ad602c3fff4bdcd386b26307
Timestamp: 1665023025 Timestamp [UCT]: 2022-10-06 02:23:45 Age [y:d:h:m:s]: 02:193:10:07:15
Block: 602906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 659803 RingCT/type: yes/0
Extra: 01f84aa7ea765aa537b600019709f5b12dfea501f8ad602c3fff4bdcd386b2630702110000000375e3f0e9000000000000000000

1 output(s) for total of 6.170526181000 dcy

stealth address amount amount idx
00: 8aa1a6c772e980a84235c62f6590a697fda6baf276f04d404ecad9e5be5c768c 6.170526181000 1039061 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": 602916, "vin": [ { "gen": { "height": 602906 } } ], "vout": [ { "amount": 6170526181, "target": { "key": "8aa1a6c772e980a84235c62f6590a697fda6baf276f04d404ecad9e5be5c768c" } } ], "extra": [ 1, 248, 74, 167, 234, 118, 90, 165, 55, 182, 0, 1, 151, 9, 245, 177, 45, 254, 165, 1, 248, 173, 96, 44, 63, 255, 75, 220, 211, 134, 178, 99, 7, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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