Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9d6114ba32182fde260b0ab0d67a5ff1ed0099ce77a95e952a0c035f7410584

Tx prefix hash: 5cbb890072d402c25a38ee638903be11a91c1d914774d2c683300090a8e47168
Tx public key: c580edcb8a1e9d33331c7609d4124075552d346a651ee4e33b90313f1f14a24e
Timestamp: 1737530272 Timestamp [UCT]: 2025-01-22 07:17:52 Age [y:d:h:m:s]: 00:050:12:42:34
Block: 1202700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35932 RingCT/type: yes/0
Extra: 01c580edcb8a1e9d33331c7609d4124075552d346a651ee4e33b90313f1f14a24e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c835aeebb82b5f9812055381e0a2ee013ee68fe23de82284e7f8cea2cee8197 0.600000000000 1689365 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": 1202710, "vin": [ { "gen": { "height": 1202700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c835aeebb82b5f9812055381e0a2ee013ee68fe23de82284e7f8cea2cee8197" } } ], "extra": [ 1, 197, 128, 237, 203, 138, 30, 157, 51, 51, 28, 118, 9, 212, 18, 64, 117, 85, 45, 52, 106, 101, 30, 228, 227, 59, 144, 49, 63, 31, 20, 162, 78, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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