Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3813f63ecb656025b4f8d852be3e95495b15a7afeec95f8d7b7bf9a874b2f69

Tx prefix hash: 229fb3b714952ebee906a9f0b2062bcd9ce0f7c9c029dc59d9872083d7fa79b1
Tx public key: 0eca49713adcc322ecca685dff34b21a0e786f6cf1af820e37501d857930358a
Timestamp: 1712351214 Timestamp [UCT]: 2024-04-05 21:06:54 Age [y:d:h:m:s]: 00:233:06:44:50
Block: 994111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167028 RingCT/type: yes/0
Extra: 010eca49713adcc322ecca685dff34b21a0e786f6cf1af820e37501d857930358a02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c04940ef50ae28e6861b78fd68e27e728625e19c1ffff07e57d21d2cc4055f0c 0.600000000000 1454511 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": 994121, "vin": [ { "gen": { "height": 994111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c04940ef50ae28e6861b78fd68e27e728625e19c1ffff07e57d21d2cc4055f0c" } } ], "extra": [ 1, 14, 202, 73, 113, 58, 220, 195, 34, 236, 202, 104, 93, 255, 52, 178, 26, 14, 120, 111, 108, 241, 175, 130, 14, 55, 80, 29, 133, 121, 48, 53, 138, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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