Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfa81eebf9cce7feea6931b8b6801e5c41fb520496398a85384c56d4c8560ce7

Tx prefix hash: 1a81696157a92971c89254c42e422be47b62093b4c955042c100acde92edd699
Tx public key: 50fdc0ac27d2fa2b850f4a2e99637c424d2aa3c289ff3c16569604c586bf103b
Timestamp: 1583003288 Timestamp [UCT]: 2020-02-29 19:08:08 Age [y:d:h:m:s]: 04:346:02:36:17
Block: 74332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1140733 RingCT/type: yes/0
Extra: 0150fdc0ac27d2fa2b850f4a2e99637c424d2aa3c289ff3c16569604c586bf103b0211000000044943cd9f000000000000000000

1 output(s) for total of 348.121247966000 dcy

stealth address amount amount idx
00: 96cd08b31c9b7d8ddcd8cb7ece9e3d62d997441b5a75a8ac4014e7237e5863fd 348.121247966000 137490 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": 74342, "vin": [ { "gen": { "height": 74332 } } ], "vout": [ { "amount": 348121247966, "target": { "key": "96cd08b31c9b7d8ddcd8cb7ece9e3d62d997441b5a75a8ac4014e7237e5863fd" } } ], "extra": [ 1, 80, 253, 192, 172, 39, 210, 250, 43, 133, 15, 74, 46, 153, 99, 124, 66, 77, 42, 163, 194, 137, 255, 60, 22, 86, 150, 4, 197, 134, 191, 16, 59, 2, 17, 0, 0, 0, 4, 73, 67, 205, 159, 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