Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a62bd7902fa7306541b9d3018d35c1676c126b02de1c729e73569a5da3567b5d

Tx prefix hash: e02b55654e3d92e3e2d5dc9032611566b796092b6933e420f7bd2b0ed39085a7
Tx public key: 829eedf040bc6c4b69ba2b90567c5d0353a03f9bcf943d48a92bfea361cfbb53
Timestamp: 1724514018 Timestamp [UCT]: 2024-08-24 15:40:18 Age [y:d:h:m:s]: 00:254:12:47:19
Block: 1095004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181769 RingCT/type: yes/0
Extra: 01829eedf040bc6c4b69ba2b90567c5d0353a03f9bcf943d48a92bfea361cfbb53021100000001e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1efbb13276fe8ac4ec8dcec17a0b245ce85c4270a40f2cc2f12035c857e6f454 0.600000000000 1570131 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": 1095014, "vin": [ { "gen": { "height": 1095004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1efbb13276fe8ac4ec8dcec17a0b245ce85c4270a40f2cc2f12035c857e6f454" } } ], "extra": [ 1, 130, 158, 237, 240, 64, 188, 108, 75, 105, 186, 43, 144, 86, 124, 93, 3, 83, 160, 63, 155, 207, 148, 61, 72, 169, 43, 254, 163, 97, 207, 187, 83, 2, 17, 0, 0, 0, 1, 227, 55, 53, 142, 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