Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d63709367499fc100e1da7e17de43a2da16ffc5688dc39f7a1a6f8f79ac1451

Tx prefix hash: 71a7e7b84234e1d4e5d902fbfdd0329cdf56e88e77374021ed79a363598a2659
Tx public key: dea6f4e2044704315711e9eca645eb5377a25dc53ab37b5a12ccbd1bf5d3c7a2
Timestamp: 1702829609 Timestamp [UCT]: 2023-12-17 16:13:29 Age [y:d:h:m:s]: 01:323:14:30:40
Block: 915203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490118 RingCT/type: yes/0
Extra: 01dea6f4e2044704315711e9eca645eb5377a25dc53ab37b5a12ccbd1bf5d3c7a2021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5326e68cd2849fa632d505e2f66a661a0292b8f6611b5fe23c2aad530b899fa6 0.600000000000 1372591 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": 915213, "vin": [ { "gen": { "height": 915203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5326e68cd2849fa632d505e2f66a661a0292b8f6611b5fe23c2aad530b899fa6" } } ], "extra": [ 1, 222, 166, 244, 226, 4, 71, 4, 49, 87, 17, 233, 236, 166, 69, 235, 83, 119, 162, 93, 197, 58, 179, 123, 90, 18, 204, 189, 27, 245, 211, 199, 162, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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