Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db349b7a0b148efe8c50ed5dd0cff3616b19b9f0cf8afa631022e05d553dd0a2

Tx prefix hash: eeb57043f9f1d0c4191800830630e0cb7c6b22afe4a638f6dd1449a652299c31
Tx public key: caf66b2c9a5371a1656c66e68a9208f887b0f96eba4d2d481404a9bec5a2c2b2
Timestamp: 1578849931 Timestamp [UCT]: 2020-01-12 17:25:31 Age [y:d:h:m:s]: 04:356:02:16:43
Block: 44115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1143970 RingCT/type: yes/0
Extra: 01caf66b2c9a5371a1656c66e68a9208f887b0f96eba4d2d481404a9bec5a2c2b20211000000084ac5aa02000000000000000000

1 output(s) for total of 438.358602377000 dcy

stealth address amount amount idx
00: fa53fc633dfdb8b5ff915a65637c623866735f14eeb2df011eca9472c0d0a3f3 438.358602377000 80175 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": 44125, "vin": [ { "gen": { "height": 44115 } } ], "vout": [ { "amount": 438358602377, "target": { "key": "fa53fc633dfdb8b5ff915a65637c623866735f14eeb2df011eca9472c0d0a3f3" } } ], "extra": [ 1, 202, 246, 107, 44, 154, 83, 113, 161, 101, 108, 102, 230, 138, 146, 8, 248, 135, 176, 249, 110, 186, 77, 45, 72, 20, 4, 169, 190, 197, 162, 194, 178, 2, 17, 0, 0, 0, 8, 74, 197, 170, 2, 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