Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4c55ad15e5363c3e34132166922734601788702836aa2a1cf7524dfa9d7c3c2

Tx prefix hash: 4f50363148380c26f1dcb1f0c9f21812455b5a408d4a49bac410b98ec36734b4
Tx public key: 7e6d9171f5d083a8300e2732722f60cd031f7406e05d69c9521ce1776c17d5fe
Timestamp: 1746114168 Timestamp [UCT]: 2025-05-01 15:42:48 Age [y:d:h:m:s]: 00:202:10:32:36
Block: 1273538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142399 RingCT/type: yes/0
Extra: 017e6d9171f5d083a8300e2732722f60cd031f7406e05d69c9521ce1776c17d5fe0211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6c0163e66dedf181dfa352eafce9b43c669dcf4c787b0c0febf814d524cd05f 0.600000000000 1760821 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": 1273548, "vin": [ { "gen": { "height": 1273538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6c0163e66dedf181dfa352eafce9b43c669dcf4c787b0c0febf814d524cd05f" } } ], "extra": [ 1, 126, 109, 145, 113, 245, 208, 131, 168, 48, 14, 39, 50, 114, 47, 96, 205, 3, 31, 116, 6, 224, 93, 105, 201, 82, 28, 225, 119, 108, 23, 213, 254, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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