Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7f9dc0cd5d1abc408334cb2b29fc7dec99602021f0b049e6c469781b9d1d666

Tx prefix hash: 8548ca8451c66ee9d325d64ca5a280f8760ad7edb74a6e0f0e9cc8941cbaa0ef
Tx public key: e804c8d4f8b7d023cf84bc593008aff8e3a549c66a02f43e0c2bff8193437f24
Timestamp: 1718463563 Timestamp [UCT]: 2024-06-15 14:59:23 Age [y:d:h:m:s]: 00:224:15:12:36
Block: 1044824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160699 RingCT/type: yes/0
Extra: 01e804c8d4f8b7d023cf84bc593008aff8e3a549c66a02f43e0c2bff8193437f2402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4a41330a3c04864f2b57d820f4361a1291fcfad0d3a829f3d972516cdc7cc62 0.600000000000 1514237 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": 1044834, "vin": [ { "gen": { "height": 1044824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4a41330a3c04864f2b57d820f4361a1291fcfad0d3a829f3d972516cdc7cc62" } } ], "extra": [ 1, 232, 4, 200, 212, 248, 183, 208, 35, 207, 132, 188, 89, 48, 8, 175, 248, 227, 165, 73, 198, 106, 2, 244, 62, 12, 43, 255, 129, 147, 67, 127, 36, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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