Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 747a500805e7a93c5335cbdf7a6d9dbb767c4cffd3b7787a88a1dde729627a54

Tx prefix hash: 0e350c6f3f7f92de03e6782337414ab486a7e70f67dbf964e6dedf878b637f1f
Tx public key: e8144c56afba70ee196d0048c6cc2ee7e9a02160029c23b2f1c1094786dcc96f
Timestamp: 1609213837 Timestamp [UCT]: 2020-12-29 03:50:37 Age [y:d:h:m:s]: 04:000:15:00:00
Block: 171159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1014034 RingCT/type: yes/0
Extra: 01e8144c56afba70ee196d0048c6cc2ee7e9a02160029c23b2f1c1094786dcc96f0211000002354ea414e5000000000000000000

1 output(s) for total of 166.301000478000 dcy

stealth address amount amount idx
00: 30ec29cf54f0fd2cc0fffe0c143cb214518bbb823dff72901587487338a70680 166.301000478000 321890 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": 171169, "vin": [ { "gen": { "height": 171159 } } ], "vout": [ { "amount": 166301000478, "target": { "key": "30ec29cf54f0fd2cc0fffe0c143cb214518bbb823dff72901587487338a70680" } } ], "extra": [ 1, 232, 20, 76, 86, 175, 186, 112, 238, 25, 109, 0, 72, 198, 204, 46, 231, 233, 160, 33, 96, 2, 156, 35, 178, 241, 193, 9, 71, 134, 220, 201, 111, 2, 17, 0, 0, 2, 53, 78, 164, 20, 229, 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