Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb35ee88adfc1f7f1f30cb7fc37b45fc9e952d9b1a51a5f13ff1ea7b4fa4cbcc

Tx prefix hash: ba0974b8ebd1e7405e8215ecac15bebcbd276ca4d5215a384ba4e3f7bdbc0008
Tx public key: 9ebbcde823ff8167ac5a0a82154349baeaf9186d061d68c63bb6a6e65c7466ce
Timestamp: 1742431238 Timestamp [UCT]: 2025-03-20 00:40:38 Age [y:d:h:m:s]: 00:310:02:35:18
Block: 1243064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219256 RingCT/type: yes/0
Extra: 019ebbcde823ff8167ac5a0a82154349baeaf9186d061d68c63bb6a6e65c7466ce021100000004ed95dce7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0c9bc38d9147321253cacc4d3338714e72f49f98a9ee7c48a307e0f2614f171 0.600000000000 1730049 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": 1243074, "vin": [ { "gen": { "height": 1243064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0c9bc38d9147321253cacc4d3338714e72f49f98a9ee7c48a307e0f2614f171" } } ], "extra": [ 1, 158, 187, 205, 232, 35, 255, 129, 103, 172, 90, 10, 130, 21, 67, 73, 186, 234, 249, 24, 109, 6, 29, 104, 198, 59, 182, 166, 230, 92, 116, 102, 206, 2, 17, 0, 0, 0, 4, 237, 149, 220, 231, 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