Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0eec41bc8d07a22b43c745fba3d315bed408cf4dc6f8a4f75b8c6b3566594f3

Tx prefix hash: 07dc6353adec8b5236072347e7d119be5d73c773d96d7bad3aaba338c8bd6d0b
Tx public key: 17e263e5f5a4cbf2e41f97f7c5c07a36ea98bb8d1ccc3695481872b2fbedbeb9
Timestamp: 1724926516 Timestamp [UCT]: 2024-08-29 10:15:16 Age [y:d:h:m:s]: 00:219:09:57:19
Block: 1098398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156667 RingCT/type: yes/0
Extra: 0117e263e5f5a4cbf2e41f97f7c5c07a36ea98bb8d1ccc3695481872b2fbedbeb902110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 233828b979e092ccd7d027b7ac7844e8dc3ee669f94e49aed324dd28ea5c000d 0.600000000000 1574099 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": 1098408, "vin": [ { "gen": { "height": 1098398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "233828b979e092ccd7d027b7ac7844e8dc3ee669f94e49aed324dd28ea5c000d" } } ], "extra": [ 1, 23, 226, 99, 229, 245, 164, 203, 242, 228, 31, 151, 247, 197, 192, 122, 54, 234, 152, 187, 141, 28, 204, 54, 149, 72, 24, 114, 178, 251, 237, 190, 185, 2, 17, 0, 0, 0, 6, 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