Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54c43200360f915856d3aec3a30949b605dff43e5afd3e3aec6353296ee118f0

Tx prefix hash: 70c79e34a917b9186e535e494919bb1916f2c0f297c1bf16e3e57f1e9dab34ca
Tx public key: cff5f184b2498e88598aff8d7e2b3dfa74bf77fa5f377468a818d28d0b225219
Timestamp: 1707055162 Timestamp [UCT]: 2024-02-04 13:59:22 Age [y:d:h:m:s]: 00:294:13:59:30
Block: 950221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210919 RingCT/type: yes/0
Extra: 01cff5f184b2498e88598aff8d7e2b3dfa74bf77fa5f377468a818d28d0b22521902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c19be206259560d54d10df172bc729d315cc430a8eba2f12bb451943b4c30e1a 0.600000000000 1408803 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": 950231, "vin": [ { "gen": { "height": 950221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c19be206259560d54d10df172bc729d315cc430a8eba2f12bb451943b4c30e1a" } } ], "extra": [ 1, 207, 245, 241, 132, 178, 73, 142, 136, 89, 138, 255, 141, 126, 43, 61, 250, 116, 191, 119, 250, 95, 55, 116, 104, 168, 24, 210, 141, 11, 34, 82, 25, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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