Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 351d22feceb089a9e3578117e1e043c9d61d47f449601811cdbfe4f162a18a66

Tx prefix hash: edd6186c35ec12af16b595ae5f23f798407dd235128b7e379aaebbb1f90a9833
Tx public key: 9f1968dff8665f7417eb9ce254e5280acacd71422ed63aa316efeb588c89c0f7
Timestamp: 1653001957 Timestamp [UCT]: 2022-05-19 23:12:37 Age [y:d:h:m:s]: 02:302:12:25:00
Block: 504633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 736615 RingCT/type: yes/0
Extra: 019f1968dff8665f7417eb9ce254e5280acacd71422ed63aa316efeb588c89c0f70211000000015eb576c5000000000000000000

1 output(s) for total of 13.059952176000 dcy

stealth address amount amount idx
00: d1786133c2c5fb7a3890c04eaff4f8572f15e7bf8c3cb00e78dfae021bf3661e 13.059952176000 929900 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": 504643, "vin": [ { "gen": { "height": 504633 } } ], "vout": [ { "amount": 13059952176, "target": { "key": "d1786133c2c5fb7a3890c04eaff4f8572f15e7bf8c3cb00e78dfae021bf3661e" } } ], "extra": [ 1, 159, 25, 104, 223, 248, 102, 95, 116, 23, 235, 156, 226, 84, 229, 40, 10, 202, 205, 113, 66, 46, 214, 58, 163, 22, 239, 235, 88, 140, 137, 192, 247, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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