Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b17d860263cceab5f0b638121bb5be97e8b279ace2f2b73d12b2472125e6e217

Tx prefix hash: 9567a7044b8c49dbf0fd7ed15ddc4f18e85f0285f0eadac772799bc840d4ebd3
Tx public key: 727ff0973cdb126f3192ffdf2a3bf3e6d12c4cc0eda68d0fba6adefe7cc5b7c1
Timestamp: 1724177894 Timestamp [UCT]: 2024-08-20 18:18:14 Age [y:d:h:m:s]: 00:223:16:08:28
Block: 1092202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159709 RingCT/type: yes/0
Extra: 01727ff0973cdb126f3192ffdf2a3bf3e6d12c4cc0eda68d0fba6adefe7cc5b7c1021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeb2c69eb554e041bf30513a8e62db31862b0efa0d288a8b49819375322ed626 0.600000000000 1566901 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": 1092212, "vin": [ { "gen": { "height": 1092202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeb2c69eb554e041bf30513a8e62db31862b0efa0d288a8b49819375322ed626" } } ], "extra": [ 1, 114, 127, 240, 151, 60, 219, 18, 111, 49, 146, 255, 223, 42, 59, 243, 230, 209, 44, 76, 192, 237, 166, 141, 15, 186, 106, 222, 254, 124, 197, 183, 193, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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