Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d5c3d32bdeca9bb6f2227ebdc55f58561fb6e8c75f970e5b20146f254cd27a6

Tx prefix hash: 01ddedcebce0d1db55c1c7be8f22bf941e2f810f9820c2eed323e8a8e3d604fd
Tx public key: b3b8796653262340881492f43902fa8612794eb75575802b7f0d5fb8f1e9633c
Timestamp: 1732066813 Timestamp [UCT]: 2024-11-20 01:40:13 Age [y:d:h:m:s]: 00:004:04:16:14
Block: 1157506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2983 RingCT/type: yes/0
Extra: 01b3b8796653262340881492f43902fa8612794eb75575802b7f0d5fb8f1e9633c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed678b421cec2cf4b29fdbf867ff38fd1f9eb286fbed2e9f640b8a2bad1efb86 0.600000000000 1643129 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": 1157516, "vin": [ { "gen": { "height": 1157506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed678b421cec2cf4b29fdbf867ff38fd1f9eb286fbed2e9f640b8a2bad1efb86" } } ], "extra": [ 1, 179, 184, 121, 102, 83, 38, 35, 64, 136, 20, 146, 244, 57, 2, 250, 134, 18, 121, 78, 183, 85, 117, 128, 43, 127, 13, 95, 184, 241, 233, 99, 60, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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