Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c2b5b71e82ab0c5d59d5e42a853651d5b6b1261be4ee43173f73a25a07c68a1

Tx prefix hash: 9ce84f75acad8976f81525c4ca7b166704c24bf3f0f1feba549d6f36201316e3
Tx public key: 7a2edd5d5b724e6794ae858fe1cd23f6e86372de20600bed4eebcde822704071
Timestamp: 1717405108 Timestamp [UCT]: 2024-06-03 08:58:28 Age [y:d:h:m:s]: 00:303:16:26:45
Block: 1036055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217012 RingCT/type: yes/0
Extra: 017a2edd5d5b724e6794ae858fe1cd23f6e86372de20600bed4eebcde8227040710211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82e38497972da4d567c53baeecabca2e58a40b833f6f1ea29fafbbe92b6f1e2b 0.600000000000 1504580 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": 1036065, "vin": [ { "gen": { "height": 1036055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82e38497972da4d567c53baeecabca2e58a40b833f6f1ea29fafbbe92b6f1e2b" } } ], "extra": [ 1, 122, 46, 221, 93, 91, 114, 78, 103, 148, 174, 133, 143, 225, 205, 35, 246, 232, 99, 114, 222, 32, 96, 11, 237, 78, 235, 205, 232, 34, 112, 64, 113, 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