Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b6c80fe741797606b05fc088c9e34090da666fdff835be53159b776e5e975ec

Tx prefix hash: 1e3fb4468b5a753895f682d8ee98d67db70a1de5f2b21658a3a55dabdf6a802c
Tx public key: b7ded6b26e18787d76f93308e500006527fe67970f84f5365eaffb58d6b749a2
Timestamp: 1731175521 Timestamp [UCT]: 2024-11-09 18:05:21 Age [y:d:h:m:s]: 00:199:22:30:53
Block: 1150122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142759 RingCT/type: yes/0
Extra: 01b7ded6b26e18787d76f93308e500006527fe67970f84f5365eaffb58d6b749a20211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3629aa3aa77e10d5bc9c65dfe8e61f26d9ad485b8f2611afd832d904d2e5c432 0.600000000000 1635335 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": 1150132, "vin": [ { "gen": { "height": 1150122 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3629aa3aa77e10d5bc9c65dfe8e61f26d9ad485b8f2611afd832d904d2e5c432" } } ], "extra": [ 1, 183, 222, 214, 178, 110, 24, 120, 125, 118, 249, 51, 8, 229, 0, 0, 101, 39, 254, 103, 151, 15, 132, 245, 54, 94, 175, 251, 88, 214, 183, 73, 162, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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