Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29786e1686d2d4a5db4ad544e95418afee6c5573a1c9e95df1020a297a58d312

Tx prefix hash: d90b3f4f6a5bfe022d651f0d024366ead5c16fe2aa80b99501d00e87ed54b097
Tx public key: ad0e29ff8cb32cb92b835a095464c068b960375f9537a444bc9363cbccc874c7
Timestamp: 1704015253 Timestamp [UCT]: 2023-12-31 09:34:13 Age [y:d:h:m:s]: 01:107:12:36:58
Block: 925024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337973 RingCT/type: yes/0
Extra: 01ad0e29ff8cb32cb92b835a095464c068b960375f9537a444bc9363cbccc874c70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 666de2aaab5694de2b1d5a42a44957f2ab711eadaad50b383be02de6235a3ff9 0.600000000000 1382784 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": 925034, "vin": [ { "gen": { "height": 925024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "666de2aaab5694de2b1d5a42a44957f2ab711eadaad50b383be02de6235a3ff9" } } ], "extra": [ 1, 173, 14, 41, 255, 140, 179, 44, 185, 43, 131, 90, 9, 84, 100, 192, 104, 185, 96, 55, 95, 149, 55, 164, 68, 188, 147, 99, 203, 204, 200, 116, 199, 2, 17, 0, 0, 0, 1, 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