Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4183c596bd29925622ad258a2dddb7fd7e6872dbbcb7d0f32fc919d5f10da29c

Tx prefix hash: 149717139007812a86b8ae0d482eee8ecab99f49ac53e9cc81e9f5f4979dbc3a
Tx public key: 9cd1bd3af3cb0515fd50840ec0e5f413ae1413b49f783bd617899acb72ff02b2
Timestamp: 1576930631 Timestamp [UCT]: 2019-12-21 12:17:11 Age [y:d:h:m:s]: 05:143:15:32:40
Block: 29400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1251642 RingCT/type: yes/0
Extra: 019cd1bd3af3cb0515fd50840ec0e5f413ae1413b49f783bd617899acb72ff02b202110000033ead433a0b000000000000000000

1 output(s) for total of 490.440649206000 dcy

stealth address amount amount idx
00: 8f26b9a6daff211ed2a4822426c316b9a1533a82609b0f0c769b0a55504e5b0d 490.440649206000 48254 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": 29410, "vin": [ { "gen": { "height": 29400 } } ], "vout": [ { "amount": 490440649206, "target": { "key": "8f26b9a6daff211ed2a4822426c316b9a1533a82609b0f0c769b0a55504e5b0d" } } ], "extra": [ 1, 156, 209, 189, 58, 243, 203, 5, 21, 253, 80, 132, 14, 192, 229, 244, 19, 174, 20, 19, 180, 159, 120, 59, 214, 23, 137, 154, 203, 114, 255, 2, 178, 2, 17, 0, 0, 3, 62, 173, 67, 58, 11, 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