Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6349340611b847598e701b6a12b2aafbcc02a7a913151b54badf1427251b6c45

Tx prefix hash: 21fcd2c74c56cec1fef21fcd3980093bb8d30cdd02a8d31a7ceca1e15de8d1a7
Tx public key: 0c583880bbb210b8f5b03dbdb4d3b29b75cd57e33565b6cb96a3d53c2d639d19
Timestamp: 1746185258 Timestamp [UCT]: 2025-05-02 11:27:38 Age [y:d:h:m:s]: 00:202:13:09:59
Block: 1274123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142464 RingCT/type: yes/0
Extra: 010c583880bbb210b8f5b03dbdb4d3b29b75cd57e33565b6cb96a3d53c2d639d190211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e3560bb7fdad0a25ec66033aded134fc54714e37a52cc9b12c95a8b5067233f 0.600000000000 1761414 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": 1274133, "vin": [ { "gen": { "height": 1274123 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e3560bb7fdad0a25ec66033aded134fc54714e37a52cc9b12c95a8b5067233f" } } ], "extra": [ 1, 12, 88, 56, 128, 187, 178, 16, 184, 245, 176, 61, 189, 180, 211, 178, 155, 117, 205, 87, 227, 53, 101, 182, 203, 150, 163, 213, 60, 45, 99, 157, 25, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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