Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a336bfa3681c0f7a9151131f24e92d9d26ce2430896c678d65bcf975a249477a

Tx prefix hash: cf1a528f591e521a03dd0b84c19e33cf20964454cd9790c57fbb9f37b6cc09ee
Tx public key: c4773c18df942693cb8a5c1839460a5ba1cf15e1d6695367856729a4447976ae
Timestamp: 1712303398 Timestamp [UCT]: 2024-04-05 07:49:58 Age [y:d:h:m:s]: 01:139:18:43:31
Block: 993719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358674 RingCT/type: yes/0
Extra: 01c4773c18df942693cb8a5c1839460a5ba1cf15e1d6695367856729a4447976ae0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65f64e66f4a5a3f66565b068306e94a8ed6d3ebd527febf4061582d4c1334ac1 0.600000000000 1454107 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": 993729, "vin": [ { "gen": { "height": 993719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65f64e66f4a5a3f66565b068306e94a8ed6d3ebd527febf4061582d4c1334ac1" } } ], "extra": [ 1, 196, 119, 60, 24, 223, 148, 38, 147, 203, 138, 92, 24, 57, 70, 10, 91, 161, 207, 21, 225, 214, 105, 83, 103, 133, 103, 41, 164, 68, 121, 118, 174, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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