Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37596aae3504acd4e4181b063fa5019db01723c520495fb49de65d27b6b8f276

Tx prefix hash: d114c545b0e171c06c1a8731ed990ab4f0e95e98d6d47c6fefd7294642a3bec8
Tx public key: 5c37ddad5c4c2722e01f0e845f8dfd09c316e9cba4e96266070ccd7ce4481183
Timestamp: 1698630123 Timestamp [UCT]: 2023-10-30 01:42:03 Age [y:d:h:m:s]: 01:116:15:13:56
Block: 880596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344316 RingCT/type: yes/0
Extra: 015c37ddad5c4c2722e01f0e845f8dfd09c316e9cba4e96266070ccd7ce4481183021100000005faf35c9c000000000000000000

1 output(s) for total of 0.741685709000 dcy

stealth address amount amount idx
00: e12c70d9be0e0f745257317e0bdbea793cda0082a20e546beed04f3fdb684ce9 0.741685709000 1336158 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": 880606, "vin": [ { "gen": { "height": 880596 } } ], "vout": [ { "amount": 741685709, "target": { "key": "e12c70d9be0e0f745257317e0bdbea793cda0082a20e546beed04f3fdb684ce9" } } ], "extra": [ 1, 92, 55, 221, 173, 92, 76, 39, 34, 224, 31, 14, 132, 95, 141, 253, 9, 195, 22, 233, 203, 164, 233, 98, 102, 7, 12, 205, 124, 228, 72, 17, 131, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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