Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7bbd33fd5c2148e5d1884712fcec2764dc3da058b827a17a6d0c0ac74ccc212

Tx prefix hash: 9ac8593757906f3f814c24b6de0b1abd99f8c646e46683ec810274c529b37ad1
Tx public key: 2776f830c6116a3c02a7e9e8a0bbcef1150d15b70870f5dc3785a6377cb1813f
Timestamp: 1732023835 Timestamp [UCT]: 2024-11-19 13:43:55 Age [y:d:h:m:s]: 00:210:12:11:21
Block: 1157145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150191 RingCT/type: yes/0
Extra: 012776f830c6116a3c02a7e9e8a0bbcef1150d15b70870f5dc3785a6377cb1813f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8c9b896f53623132e91027d212690249e3d1caa9c31ec48fea539b824b1d808 0.600000000000 1642768 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": 1157155, "vin": [ { "gen": { "height": 1157145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8c9b896f53623132e91027d212690249e3d1caa9c31ec48fea539b824b1d808" } } ], "extra": [ 1, 39, 118, 248, 48, 198, 17, 106, 60, 2, 167, 233, 232, 160, 187, 206, 241, 21, 13, 21, 183, 8, 112, 245, 220, 55, 133, 166, 55, 124, 177, 129, 63, 2, 17, 0, 0, 0, 2, 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