Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bc41de2bf1bf847fe417fcb022b2449fc2bfcbd51b4023e7128b9c6f7899df5

Tx prefix hash: 43a4ea504d0f9edee739237245d9010f439ba77e3c566f47a4c9e890295fce97
Tx public key: 0f4d06837376e68825e41553dcdbe1e625897a5e06ec47d5aa76634425ccdf2b
Timestamp: 1695638929 Timestamp [UCT]: 2023-09-25 10:48:49 Age [y:d:h:m:s]: 01:186:10:12:34
Block: 855786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394303 RingCT/type: yes/0
Extra: 010f4d06837376e68825e41553dcdbe1e625897a5e06ec47d5aa76634425ccdf2b02110000000333af99f4000000000000000000

1 output(s) for total of 0.896243000000 dcy

stealth address amount amount idx
00: 40f73decd40bf10738304075d823a43f6a674c473c4670a0573321e64eba2257 0.896243000000 1309828 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": 855796, "vin": [ { "gen": { "height": 855786 } } ], "vout": [ { "amount": 896243000, "target": { "key": "40f73decd40bf10738304075d823a43f6a674c473c4670a0573321e64eba2257" } } ], "extra": [ 1, 15, 77, 6, 131, 115, 118, 230, 136, 37, 228, 21, 83, 220, 219, 225, 230, 37, 137, 122, 94, 6, 236, 71, 213, 170, 118, 99, 68, 37, 204, 223, 43, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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