Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0389a07b966ae47f942ce93c5c11f04f7d183f8d514a4b75c48e0dd63f67289

Tx prefix hash: 3d469fef71344ba69bd4c9e81dfb2ed9276dc0ca69ea9aef5a964f549f577472
Tx public key: 2be66c160f5f6a50ae1e7c0c1e1adc86bbf08f8cec9fe17c4dfca168651b394c
Timestamp: 1711918971 Timestamp [UCT]: 2024-03-31 21:02:51 Age [y:d:h:m:s]: 00:337:19:30:55
Block: 990571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241502 RingCT/type: yes/0
Extra: 012be66c160f5f6a50ae1e7c0c1e1adc86bbf08f8cec9fe17c4dfca168651b394c0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ff503ec718c0cd090428073c67bd08b7914d8b82c4615ed32e5c8843af9efd3 0.600000000000 1450893 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": 990581, "vin": [ { "gen": { "height": 990571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ff503ec718c0cd090428073c67bd08b7914d8b82c4615ed32e5c8843af9efd3" } } ], "extra": [ 1, 43, 230, 108, 22, 15, 95, 106, 80, 174, 30, 124, 12, 30, 26, 220, 134, 187, 240, 143, 140, 236, 159, 225, 124, 77, 252, 161, 104, 101, 27, 57, 76, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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