Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 222bc6693d64e00c8b11ef064f84385f261f6394c819c885244fd8147f260c2a

Tx prefix hash: 3c00eabfd0fd3e735f4d607749fb0097dbf0f366daf5926e744abfd506c3fc5f
Tx public key: 1d98b7efad05828e1d29a7bf53b9a598dd97278e88f29a30c4fbf0f585d9bd7b
Timestamp: 1701588361 Timestamp [UCT]: 2023-12-03 07:26:01 Age [y:d:h:m:s]: 01:082:09:01:04
Block: 904907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319988 RingCT/type: yes/0
Extra: 011d98b7efad05828e1d29a7bf53b9a598dd97278e88f29a30c4fbf0f585d9bd7b02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.616123027000 dcy

stealth address amount amount idx
00: 3627f33d74c773c42b83f88c58f1c4cd3fd09e38b38559ffc44f914c00a3139e 0.616123027000 1361692 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": 904917, "vin": [ { "gen": { "height": 904907 } } ], "vout": [ { "amount": 616123027, "target": { "key": "3627f33d74c773c42b83f88c58f1c4cd3fd09e38b38559ffc44f914c00a3139e" } } ], "extra": [ 1, 29, 152, 183, 239, 173, 5, 130, 142, 29, 41, 167, 191, 83, 185, 165, 152, 221, 151, 39, 142, 136, 242, 154, 48, 196, 251, 240, 245, 133, 217, 189, 123, 2, 17, 0, 0, 0, 3, 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