Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93216c11b5c4c308401bf2164b29a707f17b8bceffdc80e0ba4f50a82def1fae

Tx prefix hash: 2c8686d67073d75f6304b9c489f3b1a24876c877ed7bf61c42a15d65e67a94a6
Tx public key: c4f64e97308865cf1d102d217850e4ab7acc5949eb598163aae49af56aa518ea
Timestamp: 1755670169 Timestamp [UCT]: 2025-08-20 06:09:29 Age [y:d:h:m:s]: 00:165:07:35:55
Block: 1350389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117979 RingCT/type: yes/0
Extra: 01c4f64e97308865cf1d102d217850e4ab7acc5949eb598163aae49af56aa518ea0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a7f0567d4aec13daa2cdc908c0e1a842407700e0f7d04566d2e70fd2524bc50 0.600000000000 1838334 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": 1350399, "vin": [ { "gen": { "height": 1350389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a7f0567d4aec13daa2cdc908c0e1a842407700e0f7d04566d2e70fd2524bc50" } } ], "extra": [ 1, 196, 246, 78, 151, 48, 136, 101, 207, 29, 16, 45, 33, 120, 80, 228, 171, 122, 204, 89, 73, 235, 89, 129, 99, 170, 228, 154, 245, 106, 165, 24, 234, 2, 17, 0, 0, 0, 1, 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