Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 154a6758a3f067b9ad40249f9b7d7fb84e4f3cf79b561cd4ea0aaccbee6d8e95

Tx prefix hash: 5aabef1b636f0af598ca088f49ce31f68b8d8c8b4fa2062fb2b7f84bb9fa9559
Tx public key: 01f69b11f6b9c77bebcd68f48991941521ce20ff880e1a60e71a41e5ad62d566
Timestamp: 1583537285 Timestamp [UCT]: 2020-03-06 23:28:05 Age [y:d:h:m:s]: 04:297:19:35:14
Block: 77797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107405 RingCT/type: yes/0
Extra: 0101f69b11f6b9c77bebcd68f48991941521ce20ff880e1a60e71a41e5ad62d56602110000002ed81c26c0000000000000000000

1 output(s) for total of 339.021340771000 dcy

stealth address amount amount idx
00: f9c2a211e21fcb4e9774af83e3e7692ca9a8af715a0f386ea6ee25be69674556 339.021340771000 143002 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": 77807, "vin": [ { "gen": { "height": 77797 } } ], "vout": [ { "amount": 339021340771, "target": { "key": "f9c2a211e21fcb4e9774af83e3e7692ca9a8af715a0f386ea6ee25be69674556" } } ], "extra": [ 1, 1, 246, 155, 17, 246, 185, 199, 123, 235, 205, 104, 244, 137, 145, 148, 21, 33, 206, 32, 255, 136, 14, 26, 96, 231, 26, 65, 229, 173, 98, 213, 102, 2, 17, 0, 0, 0, 46, 216, 28, 38, 192, 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