Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e32bb81e32cafa1a324d2f58ceb6a73144bbc026716efea193e030574bd75e0b

Tx prefix hash: 8f8f166c3609cfb2a6ae6421e14d79d056d6047b0c26e26fc9db089d086d7097
Tx public key: 8a62043d8c5003647b9d3bc8ac8f842d1245fcc542380d602df8e88c7bd96d6b
Timestamp: 1704471812 Timestamp [UCT]: 2024-01-05 16:23:32 Age [y:d:h:m:s]: 01:301:23:23:04
Block: 928803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 474638 RingCT/type: yes/0
Extra: 018a62043d8c5003647b9d3bc8ac8f842d1245fcc542380d602df8e88c7bd96d6b02110000001152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e88f1f0e5a69ba395b15870f6df6e088e027127bbbe0b1d078ea115257beb3a 0.600000000000 1386667 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": 928813, "vin": [ { "gen": { "height": 928803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e88f1f0e5a69ba395b15870f6df6e088e027127bbbe0b1d078ea115257beb3a" } } ], "extra": [ 1, 138, 98, 4, 61, 140, 80, 3, 100, 123, 157, 59, 200, 172, 143, 132, 45, 18, 69, 252, 197, 66, 56, 13, 96, 45, 248, 232, 140, 123, 217, 109, 107, 2, 17, 0, 0, 0, 17, 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