Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c16f70133bfb868dea56e89000016150f5ca9c983a1ec74554a50bdd3a959b4

Tx prefix hash: 8139ae17325463641bde735f193fba3f7a4526962070c2664d4d40ab257ce000
Tx public key: 88f1d007ff3a6d6e6a70f0fa29bf7744360de874911e1d2fdd093b5a6e4f7f6b
Timestamp: 1708168215 Timestamp [UCT]: 2024-02-17 11:10:15 Age [y:d:h:m:s]: 01:037:18:01:44
Block: 959460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287996 RingCT/type: yes/0
Extra: 0188f1d007ff3a6d6e6a70f0fa29bf7744360de874911e1d2fdd093b5a6e4f7f6b0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db495ccdc3eed19474b3f13b2b651e807a9e625784551824be33a51e1964541e 0.600000000000 1418995 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": 959470, "vin": [ { "gen": { "height": 959460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db495ccdc3eed19474b3f13b2b651e807a9e625784551824be33a51e1964541e" } } ], "extra": [ 1, 136, 241, 208, 7, 255, 58, 109, 110, 106, 112, 240, 250, 41, 191, 119, 68, 54, 13, 232, 116, 145, 30, 29, 47, 221, 9, 59, 90, 110, 79, 127, 107, 2, 17, 0, 0, 0, 2, 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