Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c75c0bbdaa425a8f6ab01738728fea4d2a5f29a50158c5b76891456ba4f9aab7

Tx prefix hash: a8d311376fdbe3f5166d847ce6ef5d1b7416fea8d0efc3dc949d796536aaff80
Tx public key: e30e6ab78da4cb5ed1cecae74d48da527b81b77f4546a80a80de7e08785735a8
Timestamp: 1751732497 Timestamp [UCT]: 2025-07-05 16:21:37 Age [y:d:h:m:s]: 00:128:08:11:52
Block: 1319356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90089 RingCT/type: yes/0
Extra: 01e30e6ab78da4cb5ed1cecae74d48da527b81b77f4546a80a80de7e08785735a80211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bb9255014efc46116927b9723e6b28c828e59e95ba4ecfd671ba76b9827e2f2 0.600000000000 1807047 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": 1319366, "vin": [ { "gen": { "height": 1319356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bb9255014efc46116927b9723e6b28c828e59e95ba4ecfd671ba76b9827e2f2" } } ], "extra": [ 1, 227, 14, 106, 183, 141, 164, 203, 94, 209, 206, 202, 231, 77, 72, 218, 82, 123, 129, 183, 127, 69, 70, 168, 10, 128, 222, 126, 8, 120, 87, 53, 168, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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