Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 166c4c90441cc0c031dec8356226861f052074c0b69eae3ad4f84e0dcd8b4086

Tx prefix hash: 0153a637e68ff0113a78c1f592f0a7ef47bb174a8f244a66ac0a8da3a0c8ef90
Tx public key: c7efc0d1939e690c0f7a7379c6df7b10b3cc883906f92ffaf1f7ccb0f0579c07
Timestamp: 1725886030 Timestamp [UCT]: 2024-09-09 12:47:10 Age [y:d:h:m:s]: 00:104:17:51:30
Block: 1106364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74929 RingCT/type: yes/0
Extra: 01c7efc0d1939e690c0f7a7379c6df7b10b3cc883906f92ffaf1f7ccb0f0579c0702110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ca10c4e92d3e10499d781e05d3de8ea02eac6fdac970423c65f1cb11ed6eaff 0.600000000000 1583963 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": 1106374, "vin": [ { "gen": { "height": 1106364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ca10c4e92d3e10499d781e05d3de8ea02eac6fdac970423c65f1cb11ed6eaff" } } ], "extra": [ 1, 199, 239, 192, 209, 147, 158, 105, 12, 15, 122, 115, 121, 198, 223, 123, 16, 179, 204, 136, 57, 6, 249, 47, 250, 241, 247, 204, 176, 240, 87, 156, 7, 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