Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b490892f3f9840aaea149b12359f91e45cead4209bc1a812430b70e2e29affc1

Tx prefix hash: 5b9aaca7a26871823a0ec3463c290aa76ba62b6f04184bf7d17549e2c45d6899
Tx public key: 9309d479b2d2cd17aaede95f0dd9f9d3a1b06b52263aac9ed2224e33237b3244
Timestamp: 1713756263 Timestamp [UCT]: 2024-04-22 03:24:23 Age [y:d:h:m:s]: 00:349:02:57:26
Block: 1005786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249587 RingCT/type: yes/0
Extra: 019309d479b2d2cd17aaede95f0dd9f9d3a1b06b52263aac9ed2224e33237b32440211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55ca8d530ebed33561fe94f4c0c88d9d7f30040185cd5320ccc6708871efe262 0.600000000000 1466586 of 15

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": 1005796, "vin": [ { "gen": { "height": 1005786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55ca8d530ebed33561fe94f4c0c88d9d7f30040185cd5320ccc6708871efe262" } } ], "extra": [ 1, 147, 9, 212, 121, 178, 210, 205, 23, 170, 237, 233, 95, 13, 217, 249, 211, 161, 176, 107, 82, 38, 58, 172, 158, 210, 34, 78, 51, 35, 123, 50, 68, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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