Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12eb28b71ca4f4c62ac127fd4641a73a6e49ad0d296fa77171c51f46cfc9d379

Tx prefix hash: 4a3ab22fe4e9e227f1557fc91332cb2e4065f2c3b9f4486d717684b60f00e76d
Tx public key: 631e65860bcbb829af22338bfc0c5a4fc2be5577f97ddc225a1a1c3382f4df96
Timestamp: 1702267756 Timestamp [UCT]: 2023-12-11 04:09:16 Age [y:d:h:m:s]: 01:106:10:41:48
Block: 910543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337197 RingCT/type: yes/0
Extra: 01631e65860bcbb829af22338bfc0c5a4fc2be5577f97ddc225a1a1c3382f4df9602110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 899ed63775659be1793a4ff8aae3358fec0d496833ad6af3db9df4aa6d0bc357 0.600000000000 1367704 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": 910553, "vin": [ { "gen": { "height": 910543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "899ed63775659be1793a4ff8aae3358fec0d496833ad6af3db9df4aa6d0bc357" } } ], "extra": [ 1, 99, 30, 101, 134, 11, 203, 184, 41, 175, 34, 51, 139, 252, 12, 90, 79, 194, 190, 85, 119, 249, 125, 220, 34, 90, 26, 28, 51, 130, 244, 223, 150, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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