Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e53d4602010d8c4b55f80d675f3a45141037d3e0d54421471e6810ef87a1c364

Tx prefix hash: 90001b4f110a21c2f7c1e9ed707e63e2aca69918558d58fda527c3a3b41845be
Tx public key: 9ce575a0b64322974586d94299d211d82743c9ff9684ddf789f94443ba0c78a9
Timestamp: 1730684643 Timestamp [UCT]: 2024-11-04 01:44:03 Age [y:d:h:m:s]: 00:157:21:15:19
Block: 1146057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112668 RingCT/type: yes/0
Extra: 019ce575a0b64322974586d94299d211d82743c9ff9684ddf789f94443ba0c78a9021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7acf3577b7e7a0efd5f514b2b559a78287ec0ecf64682c92a4e370e6ce2ccc04 0.600000000000 1630616 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": 1146067, "vin": [ { "gen": { "height": 1146057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7acf3577b7e7a0efd5f514b2b559a78287ec0ecf64682c92a4e370e6ce2ccc04" } } ], "extra": [ 1, 156, 229, 117, 160, 182, 67, 34, 151, 69, 134, 217, 66, 153, 210, 17, 216, 39, 67, 201, 255, 150, 132, 221, 247, 137, 249, 68, 67, 186, 12, 120, 169, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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