Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 020e8294eccfa51a9d003651e87b80c27d23cd5782c471e817d2b610c1252613

Tx prefix hash: 69c9ab1cf81d966f534bc197a19df4b421d1003071bfc7a790d642b7ea49bd9e
Tx public key: 7db436a04b93f0c7bbce3036e3a5311371e8a09300706883faeef901a9b840ca
Timestamp: 1713069425 Timestamp [UCT]: 2024-04-14 04:37:05 Age [y:d:h:m:s]: 00:361:11:37:22
Block: 1000078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258449 RingCT/type: yes/0
Extra: 017db436a04b93f0c7bbce3036e3a5311371e8a09300706883faeef901a9b840ca02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db69ca0aa7a9b9e445d7576ca2e176a085356f6573d1c1beace8bdaacb3a7315 0.600000000000 1460568 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": 1000088, "vin": [ { "gen": { "height": 1000078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db69ca0aa7a9b9e445d7576ca2e176a085356f6573d1c1beace8bdaacb3a7315" } } ], "extra": [ 1, 125, 180, 54, 160, 75, 147, 240, 199, 187, 206, 48, 54, 227, 165, 49, 19, 113, 232, 160, 147, 0, 112, 104, 131, 250, 238, 249, 1, 169, 184, 64, 202, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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