Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4aafc83e1985e057c2a256b1b79bba6a8fd6f1a1722320c5acbc7aa5e6107e56

Tx prefix hash: e1ef2d0bdfb86c1271a138beeaec3f2e176ebbf2cf6fa36314da042c906855d5
Tx public key: b72e00e0ed0e5be8adf938108037b8ef6fc2c0bdd08ff23d44f325ecab7833c8
Timestamp: 1706332818 Timestamp [UCT]: 2024-01-27 05:20:18 Age [y:d:h:m:s]: 01:076:19:54:43
Block: 944216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316001 RingCT/type: yes/0
Extra: 01b72e00e0ed0e5be8adf938108037b8ef6fc2c0bdd08ff23d44f325ecab7833c80211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c18f1894d824e08e7b3ea1ed674e13c8b83a8f4ce3b0afb386eaa344ccf49d1 0.600000000000 1402452 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": 944226, "vin": [ { "gen": { "height": 944216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c18f1894d824e08e7b3ea1ed674e13c8b83a8f4ce3b0afb386eaa344ccf49d1" } } ], "extra": [ 1, 183, 46, 0, 224, 237, 14, 91, 232, 173, 249, 56, 16, 128, 55, 184, 239, 111, 194, 192, 189, 208, 143, 242, 61, 68, 243, 37, 236, 171, 120, 51, 200, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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