Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9e0704e2ea19bf05f144f1f80e849de0d6eef53eb27eb2a1522026f75bc54c6

Tx prefix hash: e61bc8aabb9962cbc4ec5d0327d290f53c7fbbfe37093e9da5231541f62ac740
Tx public key: 567e175f5aaced2fb0e9508faee97c9836b0f3e7b5d5fb067e0f0993032ff13f
Timestamp: 1715870848 Timestamp [UCT]: 2024-05-16 14:47:28 Age [y:d:h:m:s]: 00:325:10:34:21
Block: 1023325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232599 RingCT/type: yes/0
Extra: 01567e175f5aaced2fb0e9508faee97c9836b0f3e7b5d5fb067e0f0993032ff13f02110000000fe08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f0908a7c664de711b030fc34ec98e0a099f1a179ae7116edc28df4a0d4bf4e9 0.600000000000 1488220 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": 1023335, "vin": [ { "gen": { "height": 1023325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f0908a7c664de711b030fc34ec98e0a099f1a179ae7116edc28df4a0d4bf4e9" } } ], "extra": [ 1, 86, 126, 23, 95, 90, 172, 237, 47, 176, 233, 80, 143, 174, 233, 124, 152, 54, 176, 243, 231, 181, 213, 251, 6, 126, 15, 9, 147, 3, 47, 241, 63, 2, 17, 0, 0, 0, 15, 224, 133, 50, 182, 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