Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7ae6c411ec361d0dfecdb96de5112486132ad432f4187da4e6c8ef6c7108c68

Tx prefix hash: 26d9ee4ae0d43ff19cf655b24986ca2a1bc6129d26663d719e3e396586e735d2
Tx public key: 0e0a4198b1916874cba0ea27966f9900d6153f4edb4d64b36d0a9a39b7b561ba
Timestamp: 1724134247 Timestamp [UCT]: 2024-08-20 06:10:47 Age [y:d:h:m:s]: 00:255:12:25:50
Block: 1091839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182497 RingCT/type: yes/0
Extra: 010e0a4198b1916874cba0ea27966f9900d6153f4edb4d64b36d0a9a39b7b561ba02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3575224975c729353051f608457a38f84d14005006d922fd652e2032a60663f4 0.600000000000 1566474 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": 1091849, "vin": [ { "gen": { "height": 1091839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3575224975c729353051f608457a38f84d14005006d922fd652e2032a60663f4" } } ], "extra": [ 1, 14, 10, 65, 152, 177, 145, 104, 116, 203, 160, 234, 39, 150, 111, 153, 0, 214, 21, 63, 78, 219, 77, 100, 179, 109, 10, 154, 57, 183, 181, 97, 186, 2, 17, 0, 0, 0, 2, 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