Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cad4d03a86228020397b542487ddc64cfd378705f12e9932999dd0db5168f33

Tx prefix hash: 822dc6706e7bd261e12b2281c87cf050eccf89c34e39e513c50fed6d8ae44dcb
Tx public key: 122a24adcb4299e76eae9d0bd3c41ad3aded47b0cdfc621ec1a7ca4f428a8867
Timestamp: 1661325753 Timestamp [UCT]: 2022-08-24 07:22:33 Age [y:d:h:m:s]: 02:236:14:51:15
Block: 572637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 690361 RingCT/type: yes/0
Extra: 01122a24adcb4299e76eae9d0bd3c41ad3aded47b0cdfc621ec1a7ca4f428a8867021100000003faf35c9c000000000000000000

1 output(s) for total of 7.773489301000 dcy

stealth address amount amount idx
00: 711644144a9557afc9c3440443cdca7a614df5da89c6ca3a949a7bd3ed2f48c5 7.773489301000 1005895 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": 572647, "vin": [ { "gen": { "height": 572637 } } ], "vout": [ { "amount": 7773489301, "target": { "key": "711644144a9557afc9c3440443cdca7a614df5da89c6ca3a949a7bd3ed2f48c5" } } ], "extra": [ 1, 18, 42, 36, 173, 203, 66, 153, 231, 110, 174, 157, 11, 211, 196, 26, 211, 173, 237, 71, 176, 205, 252, 98, 30, 193, 167, 202, 79, 66, 138, 136, 103, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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