Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4143704034f4f86305e83964ab6bc16c7416b96db771dc646934643540fa3ea

Tx prefix hash: a318909b86f1c7acb5fe04bb7a5e3acf3c50d8f4bb4a56078d11fdc1b5e1ac75
Tx public key: fc6870e3aaec7967c5fef850ec29be5fefd627aaf9a5738141eb21b2f8872ca3
Timestamp: 1757480915 Timestamp [UCT]: 2025-09-10 05:08:35 Age [y:d:h:m:s]: 00:064:18:49:40
Block: 1365207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46370 RingCT/type: yes/0
Extra: 01fc6870e3aaec7967c5fef850ec29be5fefd627aaf9a5738141eb21b2f8872ca302110000000cad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7371e3b26c57461663dae4144311163f8f344a03e05c2b75fcbb453628c6f09 0.600000000000 1853246 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": 1365217, "vin": [ { "gen": { "height": 1365207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7371e3b26c57461663dae4144311163f8f344a03e05c2b75fcbb453628c6f09" } } ], "extra": [ 1, 252, 104, 112, 227, 170, 236, 121, 103, 197, 254, 248, 80, 236, 41, 190, 95, 239, 214, 39, 170, 249, 165, 115, 129, 65, 235, 33, 178, 248, 135, 44, 163, 2, 17, 0, 0, 0, 12, 173, 121, 72, 208, 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