Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 557f8bb46a123108bdaf82bf37650f168b65de813052013488d84785345754f3

Tx prefix hash: 9eb6a419842b9c19aebbe915df9add323506e76ec3a0d377c3d0d433f30aed82
Tx public key: ec0302e2a1dab8b0d682b11b9c51f247effff5e5cda32421e9ea251b0e191d55
Timestamp: 1653069801 Timestamp [UCT]: 2022-05-20 18:03:21 Age [y:d:h:m:s]: 02:362:20:23:07
Block: 505186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 779758 RingCT/type: yes/0
Extra: 01ec0302e2a1dab8b0d682b11b9c51f247effff5e5cda32421e9ea251b0e191d5502110000000fe6d27f9c000000000000000000

1 output(s) for total of 13.005127381000 dcy

stealth address amount amount idx
00: 1fbcfbcecef7e9b7cb1b00e9a7ae2c4fcf5fa5c0d7510e48b4d57f6612d99292 13.005127381000 930551 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": 505196, "vin": [ { "gen": { "height": 505186 } } ], "vout": [ { "amount": 13005127381, "target": { "key": "1fbcfbcecef7e9b7cb1b00e9a7ae2c4fcf5fa5c0d7510e48b4d57f6612d99292" } } ], "extra": [ 1, 236, 3, 2, 226, 161, 218, 184, 176, 214, 130, 177, 27, 156, 81, 242, 71, 239, 255, 245, 229, 205, 163, 36, 33, 233, 234, 37, 27, 14, 25, 29, 85, 2, 17, 0, 0, 0, 15, 230, 210, 127, 156, 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