Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ecca5d4ea8bd561145ec568e1c5cbc5706d4f415a2c7927b1f82c4f2371db7c

Tx prefix hash: 4bf34aae4d85f262629242288e7ecef9034502de160144fbeeb60f145e9303e3
Tx public key: 07e901dfe1b69a24a65643f919f18fdcd28c6300e0d8c9ac1f9f30714baeeb77
Timestamp: 1761732259 Timestamp [UCT]: 2025-10-29 10:04:19 Age [y:d:h:m:s]: 00:015:22:48:07
Block: 1400421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11419 RingCT/type: yes/0
Extra: 0107e901dfe1b69a24a65643f919f18fdcd28c6300e0d8c9ac1f9f30714baeeb770211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 977907ef9d4888ade48cc84efd6c7d8eb671e4a98368061b2545ff939facbad0 0.600000000000 1888728 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": 1400431, "vin": [ { "gen": { "height": 1400421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "977907ef9d4888ade48cc84efd6c7d8eb671e4a98368061b2545ff939facbad0" } } ], "extra": [ 1, 7, 233, 1, 223, 225, 182, 154, 36, 166, 86, 67, 249, 25, 241, 143, 220, 210, 140, 99, 0, 224, 216, 201, 172, 31, 159, 48, 113, 75, 174, 235, 119, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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