Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 157e3bd8cc40859e099073e47e1c8cba36e0fb4dee0e41e3a75a1616e27ff4c9

Tx prefix hash: 26758f8caf036aa3360b07e92db5108426f023196fc939947ea21c5065cf4372
Tx public key: 0f868959fa520234f2cb4d5cadda1704ba60fe7c1f9d1731e449e1162d1c48f8
Timestamp: 1577611501 Timestamp [UCT]: 2019-12-29 09:25:01 Age [y:d:h:m:s]: 05:035:13:20:45
Block: 34212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175161 RingCT/type: yes/0
Extra: 010f868959fa520234f2cb4d5cadda1704ba60fe7c1f9d1731e449e1162d1c48f802110000000d8a2ee0d9000000000000000000

1 output(s) for total of 472.761713478000 dcy

stealth address amount amount idx
00: f1bedfa0b2b13f04e49c629a2073c7c2be31dc0ed57236d05fb79879c4f315cc 472.761713478000 57582 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": 34222, "vin": [ { "gen": { "height": 34212 } } ], "vout": [ { "amount": 472761713478, "target": { "key": "f1bedfa0b2b13f04e49c629a2073c7c2be31dc0ed57236d05fb79879c4f315cc" } } ], "extra": [ 1, 15, 134, 137, 89, 250, 82, 2, 52, 242, 203, 77, 92, 173, 218, 23, 4, 186, 96, 254, 124, 31, 157, 23, 49, 228, 73, 225, 22, 45, 28, 72, 248, 2, 17, 0, 0, 0, 13, 138, 46, 224, 217, 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