Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73737e43091b378e0e581873451ec9f66222bfd76976d41e9f74bb49ada330d4

Tx prefix hash: ac1733cd6a31ac0d7085a457a24189bd04135e0fa62d4dfc81697a239c5e77fc
Tx public key: ae9d2d0ec00e37a6edf0d423c509070d35d3ee12f78eed243a2fb8de3b380f3e
Timestamp: 1694006954 Timestamp [UCT]: 2023-09-06 13:29:14 Age [y:d:h:m:s]: 01:207:17:18:48
Block: 842240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409564 RingCT/type: yes/0
Extra: 01ae9d2d0ec00e37a6edf0d423c509070d35d3ee12f78eed243a2fb8de3b380f3e02110000000ce6d27f9c000000000000000000

1 output(s) for total of 0.993823627000 dcy

stealth address amount amount idx
00: 6098c2c8e35d89533d60a7c18d7720a7523f0f90950dc5c17fb8c4cbff176723 0.993823627000 1295348 of 0

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": 842250, "vin": [ { "gen": { "height": 842240 } } ], "vout": [ { "amount": 993823627, "target": { "key": "6098c2c8e35d89533d60a7c18d7720a7523f0f90950dc5c17fb8c4cbff176723" } } ], "extra": [ 1, 174, 157, 45, 14, 192, 14, 55, 166, 237, 240, 212, 35, 197, 9, 7, 13, 53, 211, 238, 18, 247, 142, 237, 36, 58, 47, 184, 222, 59, 56, 15, 62, 2, 17, 0, 0, 0, 12, 230, 210, 127, 156, 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