Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0d2439c43d219e79d0b88372c1118773a3db3d72f43a73e072da7ccbb7d3e43

Tx prefix hash: 261809df45c85ba9edb93e6579dcfc2d232d92133743ba85f37c4e5e4cb1b0da
Tx public key: b7cde2a7e650a741e128b32c3e326e7238c0a2f11860942583c51a5678701fc6
Timestamp: 1764503044 Timestamp [UCT]: 2025-11-30 11:44:04 Age [y:d:h:m:s]: 00:039:20:10:50
Block: 1423385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28523 RingCT/type: yes/0
Extra: 01b7cde2a7e650a741e128b32c3e326e7238c0a2f11860942583c51a5678701fc602110000000670609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e88cb941657c29bb8e05e3600cebf223fb2ce910b54959789bc888cb3508c340 0.600000000000 1911994 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": 1423395, "vin": [ { "gen": { "height": 1423385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e88cb941657c29bb8e05e3600cebf223fb2ce910b54959789bc888cb3508c340" } } ], "extra": [ 1, 183, 205, 226, 167, 230, 80, 167, 65, 225, 40, 179, 44, 62, 50, 110, 114, 56, 192, 162, 241, 24, 96, 148, 37, 131, 197, 26, 86, 120, 112, 31, 198, 2, 17, 0, 0, 0, 6, 112, 96, 157, 3, 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