Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04c53facd8fda596d02b53bddc95b1896dfc62b4f46c02e894a6135f002677ac

Tx prefix hash: a0d1c415051b132b2836f737827a9a5c1ad4e29b1b8d1ecffb212244b3cbef19
Tx public key: 174a9a915a09f9ec81110ad4170f39448b9fb32eb1bd71793d68c8c1bdf56ebe
Timestamp: 1580797162 Timestamp [UCT]: 2020-02-04 06:19:22 Age [y:d:h:m:s]: 04:300:09:09:33
Block: 58488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105867 RingCT/type: yes/0
Extra: 01174a9a915a09f9ec81110ad4170f39448b9fb32eb1bd71793d68c8c1bdf56ebe0211000000b049b77a3d000000000000000000

1 output(s) for total of 392.956720244000 dcy

stealth address amount amount idx
00: cc7291c58dacf78f8c581af1a9a35e268902ae51423a83a3ee2c5d2861cae8d3 392.956720244000 108029 of 0

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": 58498, "vin": [ { "gen": { "height": 58488 } } ], "vout": [ { "amount": 392956720244, "target": { "key": "cc7291c58dacf78f8c581af1a9a35e268902ae51423a83a3ee2c5d2861cae8d3" } } ], "extra": [ 1, 23, 74, 154, 145, 90, 9, 249, 236, 129, 17, 10, 212, 23, 15, 57, 68, 139, 159, 179, 46, 177, 189, 113, 121, 61, 104, 200, 193, 189, 245, 110, 190, 2, 17, 0, 0, 0, 176, 73, 183, 122, 61, 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