Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0645797adc951581e214497d0f1758d30b16ce90efb4c7b4dd02b96e1b7f4e98

Tx prefix hash: bd1309635cd5dd8eebf71fe45cb65a0e914bcd08383b9d047ac9a3a5ef8ce556
Tx public key: 977b90b6b1ecb38e7981e2b49be604d571a5594b106cca732115de175d0d5e34
Timestamp: 1716443511 Timestamp [UCT]: 2024-05-23 05:51:51 Age [y:d:h:m:s]: 00:316:20:48:54
Block: 1028071 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226469 RingCT/type: yes/0
Extra: 01977b90b6b1ecb38e7981e2b49be604d571a5594b106cca732115de175d0d5e3402110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b11523b3f7da5afaa210d4a55bacbf83a1d830dbf1ad7c29efc3141615c3a0c 0.600000000000 1495988 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": 1028081, "vin": [ { "gen": { "height": 1028071 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b11523b3f7da5afaa210d4a55bacbf83a1d830dbf1ad7c29efc3141615c3a0c" } } ], "extra": [ 1, 151, 123, 144, 182, 177, 236, 179, 142, 121, 129, 226, 180, 155, 230, 4, 213, 113, 165, 89, 75, 16, 108, 202, 115, 33, 21, 222, 23, 93, 13, 94, 52, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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