Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b9b17622de208de71c38e7b31ffc6fb33a3ff503fd5d71480fa0fd791dc3b53

Tx prefix hash: a60c2932d5ec7cdb44340efc3fdfc77e442bed8d802db0b65f3d36958d6ed6d9
Tx public key: 4f37abbb8ab5d3527264e5e42589250f3337e32c30e169d5690ce9b711876615
Timestamp: 1700482878 Timestamp [UCT]: 2023-11-20 12:21:18 Age [y:d:h:m:s]: 01:148:17:26:43
Block: 895755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367471 RingCT/type: yes/0
Extra: 014f37abbb8ab5d3527264e5e42589250f3337e32c30e169d5690ce9b711876615021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.660681018000 dcy

stealth address amount amount idx
00: 33966f312f84531191cfad0e025bad04fa6fb85b563e2bf11eda9f198a4fb837 0.660681018000 1352002 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": 895765, "vin": [ { "gen": { "height": 895755 } } ], "vout": [ { "amount": 660681018, "target": { "key": "33966f312f84531191cfad0e025bad04fa6fb85b563e2bf11eda9f198a4fb837" } } ], "extra": [ 1, 79, 55, 171, 187, 138, 181, 211, 82, 114, 100, 229, 228, 37, 137, 37, 15, 51, 55, 227, 44, 48, 225, 105, 213, 105, 12, 233, 183, 17, 135, 102, 21, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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