Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be90f868436f0cb5d468382a63cc656f0e0c30a89e417da6690d9e2e23416a15

Tx prefix hash: fc677d8b20c1b46425395c48656f433edb99693e315b9a6f0db0326fabd02c4f
Tx public key: 7c8493e42e1fdf96d6b8138b34296e3f3af7e579ab5eab747cb43443898d7dc7
Timestamp: 1578423876 Timestamp [UCT]: 2020-01-07 19:04:36 Age [y:d:h:m:s]: 04:352:18:16:38
Block: 40724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1141459 RingCT/type: yes/0
Extra: 017c8493e42e1fdf96d6b8138b34296e3f3af7e579ab5eab747cb43443898d7dc7021100000017d81c26c0000000000000000000

1 output(s) for total of 449.847518623000 dcy

stealth address amount amount idx
00: 9435f251103cf7beb2d7be0be7e512b8225a9747adaca34a208f7b873c4906e4 449.847518623000 71789 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": 40734, "vin": [ { "gen": { "height": 40724 } } ], "vout": [ { "amount": 449847518623, "target": { "key": "9435f251103cf7beb2d7be0be7e512b8225a9747adaca34a208f7b873c4906e4" } } ], "extra": [ 1, 124, 132, 147, 228, 46, 31, 223, 150, 214, 184, 19, 139, 52, 41, 110, 63, 58, 247, 229, 121, 171, 94, 171, 116, 124, 180, 52, 67, 137, 141, 125, 199, 2, 17, 0, 0, 0, 23, 216, 28, 38, 192, 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