Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 641daf885bfb688882e499224eb720e1d50d9b7babd17f8b859362feb4ddda92

Tx prefix hash: 10cea492cd1e4cf756c76425a73214725b6f7c55046264f75d16c162c0561c06
Tx public key: 535c3ab66d4fab785adb4c76b573587573159cd4b0968a37899326647dd1d4a6
Timestamp: 1629126867 Timestamp [UCT]: 2021-08-16 15:14:27 Age [y:d:h:m:s]: 03:288:23:40:33
Block: 315392 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 979601 RingCT/type: yes/0
Extra: 01535c3ab66d4fab785adb4c76b573587573159cd4b0968a37899326647dd1d4a602110000000801f1e57f000000000000000000

1 output(s) for total of 55.331933523000 dcy

stealth address amount amount idx
00: 66e9ba65a2392d4a7b5c0acf46b8bf94b9b10d33a0d3b6e618f3c7138d058ee8 55.331933523000 656433 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": 315402, "vin": [ { "gen": { "height": 315392 } } ], "vout": [ { "amount": 55331933523, "target": { "key": "66e9ba65a2392d4a7b5c0acf46b8bf94b9b10d33a0d3b6e618f3c7138d058ee8" } } ], "extra": [ 1, 83, 92, 58, 182, 109, 79, 171, 120, 90, 219, 76, 118, 181, 115, 88, 117, 115, 21, 156, 212, 176, 150, 138, 55, 137, 147, 38, 100, 125, 209, 212, 166, 2, 17, 0, 0, 0, 8, 1, 241, 229, 127, 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