Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1ff5ab1a755f27a4977209e6c1363f3d1ec0b39c54e30cd16147082e3e7d3f2

Tx prefix hash: c33f04124f5d79e43b0099b89d1a74236fc64ebcce18ae5d7dab591179c8e594
Tx public key: af879017c91b03145c6382dd87a2f14c1473783df3f6dc94cc5211ce0ea7b52d
Timestamp: 1710552474 Timestamp [UCT]: 2024-03-16 01:27:54 Age [y:d:h:m:s]: 01:019:23:06:18
Block: 979246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275243 RingCT/type: yes/0
Extra: 01af879017c91b03145c6382dd87a2f14c1473783df3f6dc94cc5211ce0ea7b52d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e235714c9400d637807fa426f3389c28b9978e2965136e9ea9081fec196cce10 0.600000000000 1439279 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": 979256, "vin": [ { "gen": { "height": 979246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e235714c9400d637807fa426f3389c28b9978e2965136e9ea9081fec196cce10" } } ], "extra": [ 1, 175, 135, 144, 23, 201, 27, 3, 20, 92, 99, 130, 221, 135, 162, 241, 76, 20, 115, 120, 61, 243, 246, 220, 148, 204, 82, 17, 206, 14, 167, 181, 45, 2, 17, 0, 0, 0, 1, 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