Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20bda76a08f95713ebdd2d443c6d530d88c551ffb0f54584722610c3cea501d6

Tx prefix hash: 9f0c1714a88015ccf33dbf5cc0094e86b9ff373f832760a6c9cb0c325711af22
Tx public key: e8532bca64df5fd3ec39ac9f32c385ef5f4fa1ca97c305129c993bfc99eed14e
Timestamp: 1730776837 Timestamp [UCT]: 2024-11-05 03:20:37 Age [y:d:h:m:s]: 00:019:15:38:59
Block: 1146810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14066 RingCT/type: yes/0
Extra: 01e8532bca64df5fd3ec39ac9f32c385ef5f4fa1ca97c305129c993bfc99eed14e021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37bf2d5baef1f254c0357fa5e1d83e62f3936358418af052e4c3c0f2fb9156fd 0.600000000000 1631501 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": 1146820, "vin": [ { "gen": { "height": 1146810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37bf2d5baef1f254c0357fa5e1d83e62f3936358418af052e4c3c0f2fb9156fd" } } ], "extra": [ 1, 232, 83, 43, 202, 100, 223, 95, 211, 236, 57, 172, 159, 50, 195, 133, 239, 95, 79, 161, 202, 151, 195, 5, 18, 156, 153, 59, 252, 153, 238, 209, 78, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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