Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557ff1df8d1cf8b82761f5711f27d27daadd78013c9099d444eb5b297dacab00

Tx prefix hash: 921485bf7fe45fb9de11ca599bf85fd2f41706d09c160d5ca406aa0ebab99267
Tx public key: e38f1b4c56b84c276f10d87388d92bdfca9c71baa6936cb815f58ede97f9c814
Timestamp: 1713650540 Timestamp [UCT]: 2024-04-20 22:02:20 Age [y:d:h:m:s]: 00:348:03:30:14
Block: 1004908 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248885 RingCT/type: yes/0
Extra: 01e38f1b4c56b84c276f10d87388d92bdfca9c71baa6936cb815f58ede97f9c8140211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c600f67c718455072473aa0bcb4e341f07a098dd0f645bb8453639893be51693 0.600000000000 1465482 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": 1004918, "vin": [ { "gen": { "height": 1004908 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c600f67c718455072473aa0bcb4e341f07a098dd0f645bb8453639893be51693" } } ], "extra": [ 1, 227, 143, 27, 76, 86, 184, 76, 39, 111, 16, 216, 115, 136, 217, 43, 223, 202, 156, 113, 186, 166, 147, 108, 184, 21, 245, 142, 222, 151, 249, 200, 20, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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