Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03798d001727ce8d3f667426cec764935922eceecf1bd9530e3ada46ee57d920

Tx prefix hash: 222875b18e5f1425e985380fbc330573acd791c349d5def451a11052f6ca9649
Tx public key: ed10bd0fd2531f042408f4efbede4fe847c2bd0b7a19f92501f74e0f1e905af8
Timestamp: 1715534882 Timestamp [UCT]: 2024-05-12 17:28:02 Age [y:d:h:m:s]: 00:311:05:59:08
Block: 1020569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222464 RingCT/type: yes/0
Extra: 01ed10bd0fd2531f042408f4efbede4fe847c2bd0b7a19f92501f74e0f1e905af802110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd88db0ad75807a1445ceb4aa74eb93d52f3b529d1c06ba178fd7df67857d6d0 0.600000000000 1484650 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": 1020579, "vin": [ { "gen": { "height": 1020569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd88db0ad75807a1445ceb4aa74eb93d52f3b529d1c06ba178fd7df67857d6d0" } } ], "extra": [ 1, 237, 16, 189, 15, 210, 83, 31, 4, 36, 8, 244, 239, 190, 222, 79, 232, 71, 194, 189, 11, 122, 25, 249, 37, 1, 247, 78, 15, 30, 144, 90, 248, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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