Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 502010a4e0438863224a58086a73a251c2ac3eab297201496d98f759b74dfb58

Tx prefix hash: e6f9c5a735b8ecd45ac7267335e8f75da71bda875f2036e1ba8c24836066dbc0
Tx public key: bd2b1fe98f1fce53f740bd124e9f68424292eeecee6cb917140f29b215959575
Timestamp: 1646032047 Timestamp [UCT]: 2022-02-28 07:07:27 Age [y:d:h:m:s]: 02:349:16:50:52
Block: 448174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 769105 RingCT/type: yes/0
Extra: 01bd2b1fe98f1fce53f740bd124e9f68424292eeecee6cb917140f29b2159595750211000000074da16a3a000000000000000000

1 output(s) for total of 20.091565316000 dcy

stealth address amount amount idx
00: db3a877e1e31e2950a8c05893dd35b10ecdbe4a4afdbcde98e97b7e24d70cd07 20.091565316000 862477 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": 448184, "vin": [ { "gen": { "height": 448174 } } ], "vout": [ { "amount": 20091565316, "target": { "key": "db3a877e1e31e2950a8c05893dd35b10ecdbe4a4afdbcde98e97b7e24d70cd07" } } ], "extra": [ 1, 189, 43, 31, 233, 143, 31, 206, 83, 247, 64, 189, 18, 78, 159, 104, 66, 66, 146, 238, 236, 238, 108, 185, 23, 20, 15, 41, 178, 21, 149, 149, 117, 2, 17, 0, 0, 0, 7, 77, 161, 106, 58, 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