Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b17feeab1f0077c90022761be18d467d2baccb7b631f2635dbcb74d470ae6b37

Tx prefix hash: 28d7d1e7f4cf0730175189aa1fefb00319243bbb19a2214124e42418742b670f
Tx public key: b31c9d8a2dd9a0710ce3233e610d076ee48f4a2898f333817575166fd220d98a
Timestamp: 1720655961 Timestamp [UCT]: 2024-07-10 23:59:21 Age [y:d:h:m:s]: 00:264:22:28:56
Block: 1062998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189265 RingCT/type: yes/0
Extra: 01b31c9d8a2dd9a0710ce3233e610d076ee48f4a2898f333817575166fd220d98a021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d914c02dfcbd8d2606ec22d428e5eeba0acad0c7ef23a19547d32b24c64d67b2 0.600000000000 1533509 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": 1063008, "vin": [ { "gen": { "height": 1062998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d914c02dfcbd8d2606ec22d428e5eeba0acad0c7ef23a19547d32b24c64d67b2" } } ], "extra": [ 1, 179, 28, 157, 138, 45, 217, 160, 113, 12, 227, 35, 62, 97, 13, 7, 110, 228, 143, 74, 40, 152, 243, 51, 129, 117, 117, 22, 111, 210, 32, 217, 138, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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