Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82ccebf114127b0b749b1816996830161375f2c471b565f3faebd9fcf990064f

Tx prefix hash: e26b11240f4fc27a2e51bba0958a30d8a551ab8d2837a5c3ef5d08c1da1e0639
Tx public key: 889e16a9c33454d0b5f5ba0a555da4e4328a010282c7e02c774890906c28ca11
Timestamp: 1707016220 Timestamp [UCT]: 2024-02-04 03:10:20 Age [y:d:h:m:s]: 01:132:09:54:33
Block: 949897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355648 RingCT/type: yes/0
Extra: 01889e16a9c33454d0b5f5ba0a555da4e4328a010282c7e02c774890906c28ca1102110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dce70789d6cb32904fc732a2f0dae591426cca8e65ee73e8e8d2b039ac8e4c7a 0.600000000000 1408433 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": 949907, "vin": [ { "gen": { "height": 949897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dce70789d6cb32904fc732a2f0dae591426cca8e65ee73e8e8d2b039ac8e4c7a" } } ], "extra": [ 1, 136, 158, 22, 169, 195, 52, 84, 208, 181, 245, 186, 10, 85, 93, 164, 228, 50, 138, 1, 2, 130, 199, 224, 44, 119, 72, 144, 144, 108, 40, 202, 17, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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