Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6a920b6427f4ac0ab1bedf61d0410d0e29c5f8385a32d9cbd7032d8ef8abc7d

Tx prefix hash: 969ad03afbbbc7c7ad94e1314495a28c9049107a4e753664cf1835ea36a3f91f
Tx public key: fdd3b801677c30c2419ce71c90a8399dbded8eb81fc7f4cca3c1ab346d943191
Timestamp: 1733991436 Timestamp [UCT]: 2024-12-12 08:17:16 Age [y:d:h:m:s]: 00:100:11:22:37
Block: 1173462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71586 RingCT/type: yes/0
Extra: 01fdd3b801677c30c2419ce71c90a8399dbded8eb81fc7f4cca3c1ab346d943191021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d3df6fb0ce2f81cacfc7f2d311645085c59ba6d07e487c199250eb03a160cb6 0.600000000000 1659487 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": 1173472, "vin": [ { "gen": { "height": 1173462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d3df6fb0ce2f81cacfc7f2d311645085c59ba6d07e487c199250eb03a160cb6" } } ], "extra": [ 1, 253, 211, 184, 1, 103, 124, 48, 194, 65, 156, 231, 28, 144, 168, 57, 157, 189, 237, 142, 184, 31, 199, 244, 204, 163, 193, 171, 52, 109, 148, 49, 145, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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