Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 264ed532ffcf174f673dcafe0e2141f9d33d31c8623d403d9fbb1800e65aac7d

Tx prefix hash: 8935985f130c6a248eb4b1c629e6df44e3005d4a21d238a8d4bc5229f493fcec
Tx public key: e8d6ce517e06408a25c05caf3101dcab7f8b9172ca946e92bb65d64f714518d2
Timestamp: 1715756199 Timestamp [UCT]: 2024-05-15 06:56:39 Age [y:d:h:m:s]: 00:240:02:03:20
Block: 1022370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171832 RingCT/type: yes/0
Extra: 01e8d6ce517e06408a25c05caf3101dcab7f8b9172ca946e92bb65d64f714518d202110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad6bc91bd5e5646945287cb165140a7b41c9b3aeb8043a9e90e397879089daab 0.600000000000 1486949 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": 1022380, "vin": [ { "gen": { "height": 1022370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad6bc91bd5e5646945287cb165140a7b41c9b3aeb8043a9e90e397879089daab" } } ], "extra": [ 1, 232, 214, 206, 81, 126, 6, 64, 138, 37, 192, 92, 175, 49, 1, 220, 171, 127, 139, 145, 114, 202, 148, 110, 146, 187, 101, 214, 79, 113, 69, 24, 210, 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