Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 255889f0ba9f05210654e90feebe8070f3f7e073d332ee0f34b93ac7023be123

Tx prefix hash: 46dcd3ec2df19601cc6e9215c0bcb3429aa2efb44fe596bbb02ec57c6b0ac7c2
Tx public key: 9a5f047723ae8e44d2643edcddce154e4a1aa7945dc786eafbdaf219f3c69e09
Timestamp: 1714408550 Timestamp [UCT]: 2024-04-29 16:35:50 Age [y:d:h:m:s]: 00:272:12:07:14
Block: 1011200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194802 RingCT/type: yes/0
Extra: 019a5f047723ae8e44d2643edcddce154e4a1aa7945dc786eafbdaf219f3c69e090211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 311fc413400ebf9adc63fa67294696006bbef890457c2ffc58af0f2eb289fd9e 0.600000000000 1473368 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": 1011210, "vin": [ { "gen": { "height": 1011200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "311fc413400ebf9adc63fa67294696006bbef890457c2ffc58af0f2eb289fd9e" } } ], "extra": [ 1, 154, 95, 4, 119, 35, 174, 142, 68, 210, 100, 62, 220, 221, 206, 21, 78, 74, 26, 167, 148, 93, 199, 134, 234, 251, 218, 242, 25, 243, 198, 158, 9, 2, 17, 0, 0, 0, 3, 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