Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb5de50b83202f93d59598e2bda8ddde032ce53515f8519724c884fbf500f906

Tx prefix hash: 108deb3b50e35f8add11faca728764f2b0917e67563c91027c76e414b8e6a119
Tx public key: 3d2958b50ae1fd97a0c6371769c48b69ab0ac83f13819d0510e75f9fae4415e2
Timestamp: 1737049626 Timestamp [UCT]: 2025-01-16 17:47:06 Age [y:d:h:m:s]: 00:152:02:23:27
Block: 1198761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108417 RingCT/type: yes/0
Extra: 013d2958b50ae1fd97a0c6371769c48b69ab0ac83f13819d0510e75f9fae4415e2021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22bfd2202a8aaa7cab6309a7e5d7e58b7ac8c58343326cb62f9a9aaae2e05a1f 0.600000000000 1685388 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": 1198771, "vin": [ { "gen": { "height": 1198761 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22bfd2202a8aaa7cab6309a7e5d7e58b7ac8c58343326cb62f9a9aaae2e05a1f" } } ], "extra": [ 1, 61, 41, 88, 181, 10, 225, 253, 151, 160, 198, 55, 23, 105, 196, 139, 105, 171, 10, 200, 63, 19, 129, 157, 5, 16, 231, 95, 159, 174, 68, 21, 226, 2, 17, 0, 0, 0, 1, 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