Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9ee6388c6ba9bcf5bfea0d78bee5f3733950cd54e92c2bb745e1c891188140f

Tx prefix hash: 0950811ce3b29b114517ee7cc8116e815b035953c155cb6f8fa1dfd8e8f0c4ac
Tx public key: 3d058f10aac5f38f61b20f718a47b8e5ff9c42e09a75ec1edf97f0bf71900cf9
Timestamp: 1745268915 Timestamp [UCT]: 2025-04-21 20:55:15 Age [y:d:h:m:s]: 00:022:20:42:44
Block: 1266538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16363 RingCT/type: yes/0
Extra: 013d058f10aac5f38f61b20f718a47b8e5ff9c42e09a75ec1edf97f0bf71900cf9021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c51bf536d00e628d20f833810ab9d71d66c541e40fd7e97b28c90833c6b027e3 0.600000000000 1753759 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": 1266548, "vin": [ { "gen": { "height": 1266538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c51bf536d00e628d20f833810ab9d71d66c541e40fd7e97b28c90833c6b027e3" } } ], "extra": [ 1, 61, 5, 143, 16, 170, 197, 243, 143, 97, 178, 15, 113, 138, 71, 184, 229, 255, 156, 66, 224, 154, 117, 236, 30, 223, 151, 240, 191, 113, 144, 12, 249, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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