Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c9638e42a96dfabd35deba02fef7acb8691dd6155e32b877b185dc3ac72434d

Tx prefix hash: 919d03b8afbc120341d10fd25056859a37804ac1a52dd139ceda2b5f771846fa
Tx public key: 563c70f4516abedcd1e96c022c2ddec642a81cb0b92ed08f787cbb6da8042fb3
Timestamp: 1649666360 Timestamp [UCT]: 2022-04-11 08:39:20 Age [y:d:h:m:s]: 03:204:13:29:18
Block: 477838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 924376 RingCT/type: yes/0
Extra: 01563c70f4516abedcd1e96c022c2ddec642a81cb0b92ed08f787cbb6da8042fb302110000000dcb8520c2000000000000000000

1 output(s) for total of 16.022289848000 dcy

stealth address amount amount idx
00: 59e8fc06bbddee9f465c000b1df4ae3bcc0b96877ff0c27d3fa21dcac9113fe2 16.022289848000 898541 of 0

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": 477848, "vin": [ { "gen": { "height": 477838 } } ], "vout": [ { "amount": 16022289848, "target": { "key": "59e8fc06bbddee9f465c000b1df4ae3bcc0b96877ff0c27d3fa21dcac9113fe2" } } ], "extra": [ 1, 86, 60, 112, 244, 81, 106, 190, 220, 209, 233, 108, 2, 44, 45, 222, 198, 66, 168, 28, 176, 185, 46, 208, 143, 120, 124, 187, 109, 168, 4, 47, 179, 2, 17, 0, 0, 0, 13, 203, 133, 32, 194, 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