Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5e2c3e08f7e4b5efc955c0bd16111dd0227bd02fad20955da57ba3bc5a90e50

Tx prefix hash: 04a4fd59a5bad80d747a77965947a1c6eba23117301feac4cd51a65044f9b457
Tx public key: 6a8c2c6ac714e88f42637df182716f78a504116a612115567e4faca3b41dfd1a
Timestamp: 1725903178 Timestamp [UCT]: 2024-09-09 17:32:58 Age [y:d:h:m:s]: 00:201:15:40:54
Block: 1106496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143955 RingCT/type: yes/0
Extra: 016a8c2c6ac714e88f42637df182716f78a504116a612115567e4faca3b41dfd1a02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f158567810699a677147c2a348c419668bb80e7f1323cfc806c28f217cb62fe 0.600000000000 1584095 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": 1106506, "vin": [ { "gen": { "height": 1106496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f158567810699a677147c2a348c419668bb80e7f1323cfc806c28f217cb62fe" } } ], "extra": [ 1, 106, 140, 44, 106, 199, 20, 232, 143, 66, 99, 125, 241, 130, 113, 111, 120, 165, 4, 17, 106, 97, 33, 21, 86, 126, 79, 172, 163, 180, 29, 253, 26, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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