Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b8343706354f96bc3fe4af3e43b8a716eac327c5464036aae0ac4498d3db382

Tx prefix hash: e38d3134b4d6c3c7717fc24fdf723fcb8dde6eb0bdfed16bf6336bbeeae3fd8f
Tx public key: 87912ae014e5b400b791b100ec61acbb4ac0f9413a9d2273c765ad4407596748
Timestamp: 1707616753 Timestamp [UCT]: 2024-02-11 01:59:13 Age [y:d:h:m:s]: 00:316:05:33:40
Block: 954878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226445 RingCT/type: yes/0
Extra: 0187912ae014e5b400b791b100ec61acbb4ac0f9413a9d2273c765ad44075967480211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b04946ed416a7af622c546e85a93273bd0e61c5c806ec11c4f1e5c1b8ca085e 0.600000000000 1414160 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": 954888, "vin": [ { "gen": { "height": 954878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b04946ed416a7af622c546e85a93273bd0e61c5c806ec11c4f1e5c1b8ca085e" } } ], "extra": [ 1, 135, 145, 42, 224, 20, 229, 180, 0, 183, 145, 177, 0, 236, 97, 172, 187, 74, 192, 249, 65, 58, 157, 34, 115, 199, 101, 173, 68, 7, 89, 103, 72, 2, 17, 0, 0, 0, 6, 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