Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c2bf217fc40ec8d60f683eaa293d65e86d207d41aa00f18ec0b19944173b432

Tx prefix hash: 5e0409993b2895e6af6bd355361166e942acd442f0149c09451377778b71c4f2
Tx public key: 60447c9150d2a9dcd43161ddbbe7d32a539baf743e490cf10ee2fc0ea9b83a3a
Timestamp: 1720002763 Timestamp [UCT]: 2024-07-03 10:32:43 Age [y:d:h:m:s]: 00:349:07:39:01
Block: 1057581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249532 RingCT/type: yes/0
Extra: 0160447c9150d2a9dcd43161ddbbe7d32a539baf743e490cf10ee2fc0ea9b83a3a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a39673108f1cd5fae6f803a78eeaa558cf75a4e200e2d860cb4e04f98d7d8f7 0.600000000000 1528018 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": 1057591, "vin": [ { "gen": { "height": 1057581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a39673108f1cd5fae6f803a78eeaa558cf75a4e200e2d860cb4e04f98d7d8f7" } } ], "extra": [ 1, 96, 68, 124, 145, 80, 210, 169, 220, 212, 49, 97, 221, 187, 231, 211, 42, 83, 155, 175, 116, 62, 73, 12, 241, 14, 226, 252, 14, 169, 184, 58, 58, 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