Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a1c2a2184a593ab721f3b9b02700e78f722afe8c7cb920cb5638718ca5f4507

Tx prefix hash: a1ffce220769aa9f930921de7ae6423d95a7ea7c55350ada7b1e281993749c8b
Tx public key: 8c73dc1b06c507eec41ab45954f33c3b170933f4a88905e1ba4591574cfd68fd
Timestamp: 1729141526 Timestamp [UCT]: 2024-10-17 05:05:26 Age [y:d:h:m:s]: 00:207:23:19:12
Block: 1133343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148436 RingCT/type: yes/0
Extra: 018c73dc1b06c507eec41ab45954f33c3b170933f4a88905e1ba4591574cfd68fd02110000000f3cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36d0f1a04c712324c52cea58d2102cd1e05c7297358f442c93ebb1249bd6a518 0.600000000000 1616444 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": 1133353, "vin": [ { "gen": { "height": 1133343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36d0f1a04c712324c52cea58d2102cd1e05c7297358f442c93ebb1249bd6a518" } } ], "extra": [ 1, 140, 115, 220, 27, 6, 197, 7, 238, 196, 26, 180, 89, 84, 243, 60, 59, 23, 9, 51, 244, 168, 137, 5, 225, 186, 69, 145, 87, 76, 253, 104, 253, 2, 17, 0, 0, 0, 15, 60, 208, 252, 6, 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